Implement separate storage buckets in flyte-core #4675
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Tracking issue
Closes #4291
Why are the changes needed?
What changes were proposed in this pull request?
This PR introduces a new mandatory field in the flyte-core Helm chart:
userBucketName
.By default it can be the same as the
bucketName
but, if different,userBucketName
will be used by Flyte to build therawoutput-prefix
parameter for propeller and, consequently, Flyte will store raw data there, storing metadata only on the storage container specified inbucketName
How was this patch tested?
Scenarios tested:
userBucketName
thanbucketName
: workflow executions store inputs/outputs in the userBucketNameuserBucketName
asbucketName
: workflow executions store both raw data and metadata on the same bucketSetup process
Screenshots
Check all the applicable boxes
Related PRs
Docs link